knitr::opts_chunk$set(echo = TRUE)
The app appears to be focused on the data exploration phase of the NPS dataset instead of focusing on a random-forest analysis (which was not completed in the initial version).
Is it clear how the results were computed?
Did the analytic work?
The actual package NPS
installed without any problems.
parcoords
was not installed originally as a dependency for NPS
. This resulted in an error when NPS::myparacoords(dataSource = dataSource)
was called. However with a quick search parcoords
was easily installed and then all functions appeared to operate correctly.The map did not properly load for some reason.
Were error encountered when executing code according to the documentation?
The analytic is very easy to use and has a very good and clean appearance to it. The challenge to me is that I have never worked with the dataset before so some of the x-axis and y-axis values options do not mean anything to me. However if I understood what the variable alluded to, it would be very convenient to switch between them all.
Are the visualization interpretable?
The NPS
package has a very easy to use and understand shiny app that will make exploring the data a breeze. Once the data selection bug and the maps work it will be a great app. Overall I feel the app is excellent.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.